NTISthis.com

Evidence Guide: ICTSAS402 - Implement configuration management strategies

Student: __________________________________________________

Signature: _________________________________________________

Tips for gathering evidence to demonstrate your skills

The important thing to remember when gathering evidence is that the more evidence the better - that is, the more evidence you gather to demonstrate your skills, the more confident an assessor can be that you have learned the skills not just at one point in time, but are continuing to apply and develop those skills (as opposed to just learning for the test!). Furthermore, one piece of evidence that you collect will not usualy demonstrate all the required criteria for a unit of competency, whereas multiple overlapping pieces of evidence will usually do the trick!

From the Wiki University

 

ICTSAS402 - Implement configuration management strategies

What evidence can you provide to prove your understanding of each of the following citeria?

Identify and clarify configuration management requirements

  1. Develop and assemble identification standards for the naming and version control of software and documentation, and provide to stakeholders
  2. Identify software configuration tools and procedures for the required level of integration into the programming environment
  3. Identify responsibilities for configuration management within the project and for ongoing support, including approval of changes
  4. Take action to ensure that stakeholders are aware of their roles
  5. Identify point at which items are subjected to configuration control with stakeholders
Develop and assemble identification standards for the naming and version control of software and documentation, and provide to stakeholders

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Identify software configuration tools and procedures for the required level of integration into the programming environment

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Identify responsibilities for configuration management within the project and for ongoing support, including approval of changes

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Take action to ensure that stakeholders are aware of their roles

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Identify point at which items are subjected to configuration control with stakeholders

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Employ appropriate control mechanisms

  1. Identify and document method for identification and recording of change requests in line with organisational requirements, and ensure this is maintained during development process
  2. Take action to ensure evaluation criteria and process for approval of change requests are employed according to organisational requirements
  3. Take action to ensure other management, security and access control criteria are employed according to organisational requirements
  4. Implement controls to ensure that necessary audit trials and alerts for variations or non-conformance are continuously maintained during development
Identify and document method for identification and recording of change requests in line with organisational requirements, and ensure this is maintained during development process

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Take action to ensure evaluation criteria and process for approval of change requests are employed according to organisational requirements

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Take action to ensure other management, security and access control criteria are employed according to organisational requirements

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Implement controls to ensure that necessary audit trials and alerts for variations or non-conformance are continuously maintained during development

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Implement monitoring mechanisms

  1. Implement controls to ensure mechanisms to identify software status throughout the software development life cycle are continuously maintained
  2. Document development and maintenance of records and status reports required to show the history of baselines and their links to backups
  3. Take action to ensure level of detail required in status reports, and identification of target audiences, meet the configuration management procedures, International Organization for Standardization (ISO), International Electrotechnical Commission (IEC) and Australian Standards (AS) and organisational requirements
  4. Integrate configuration management into general project management processes for monitoring and control purposes and document
Implement controls to ensure mechanisms to identify software status throughout the software development life cycle are continuously maintained

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Document development and maintenance of records and status reports required to show the history of baselines and their links to backups

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Take action to ensure level of detail required in status reports, and identification of target audiences, meet the configuration management procedures, International Organization for Standardization (ISO), International Electrotechnical Commission (IEC) and Australian Standards (AS) and organisational requirements

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Integrate configuration management into general project management processes for monitoring and control purposes and document

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Manage release of product

  1. Take action to ensure physical and functional completeness of items for release to all stakeholders
  2. Identify and implement requirements for formal control of software products
  3. Determine and document policies for retention of baseline or master copies, taking into account safety and security, legislative requirements and organisational guidelines
Take action to ensure physical and functional completeness of items for release to all stakeholders

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Identify and implement requirements for formal control of software products

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Determine and document policies for retention of baseline or master copies, taking into account safety and security, legislative requirements and organisational guidelines

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Assessed

Teacher: ___________________________________ Date: _________

Signature: ________________________________________________

Comments:

 

 

 

 

 

 

 

 

Instructions to Assessors

Evidence Guide

ELEMENT

PERFORMANCE CRITERIA

Elements describe the essential outcomes.

Performance criteria describe the performance needed to demonstrate achievement of the element.

1. Identify and clarify configuration management requirements

1.1 Develop and assemble identification standards for the naming and version control of software and documentation, and provide to stakeholders

1.2 Identify software configuration tools and procedures for the required level of integration into the programming environment

1.3 Identify responsibilities for configuration management within the project and for ongoing support, including approval of changes

1.4 Take action to ensure that stakeholders are aware of their roles

1.5 Identify point at which items are subjected to configuration control with stakeholders

2. Employ appropriate control mechanisms

2.1 Identify and document method for identification and recording of change requests in line with organisational requirements, and ensure this is maintained during development process

2.2 Take action to ensure evaluation criteria and process for approval of change requests are employed according to organisational requirements

2.3 Take action to ensure other management, security and access control criteria are employed according to organisational requirements

2.4 Implement controls to ensure that necessary audit trials and alerts for variations or non-conformance are continuously maintained during development

3. Implement monitoring mechanisms

3.1 Implement controls to ensure mechanisms to identify software status throughout the software development life cycle are continuously maintained

3.2 Document development and maintenance of records and status reports required to show the history of baselines and their links to backups

3.3 Take action to ensure level of detail required in status reports, and identification of target audiences, meet the configuration management procedures, International Organization for Standardization (ISO), International Electrotechnical Commission (IEC) and Australian Standards (AS) and organisational requirements

3.4 Integrate configuration management into general project management processes for monitoring and control purposes and document

4. Manage release of product

4.1 Take action to ensure physical and functional completeness of items for release to all stakeholders

4.2 Identify and implement requirements for formal control of software products

4.3 Determine and document policies for retention of baseline or master copies, taking into account safety and security, legislative requirements and organisational guidelines

Required Skills and Knowledge

ELEMENT

PERFORMANCE CRITERIA

Elements describe the essential outcomes.

Performance criteria describe the performance needed to demonstrate achievement of the element.

1. Identify and clarify configuration management requirements

1.1 Develop and assemble identification standards for the naming and version control of software and documentation, and provide to stakeholders

1.2 Identify software configuration tools and procedures for the required level of integration into the programming environment

1.3 Identify responsibilities for configuration management within the project and for ongoing support, including approval of changes

1.4 Take action to ensure that stakeholders are aware of their roles

1.5 Identify point at which items are subjected to configuration control with stakeholders

2. Employ appropriate control mechanisms

2.1 Identify and document method for identification and recording of change requests in line with organisational requirements, and ensure this is maintained during development process

2.2 Take action to ensure evaluation criteria and process for approval of change requests are employed according to organisational requirements

2.3 Take action to ensure other management, security and access control criteria are employed according to organisational requirements

2.4 Implement controls to ensure that necessary audit trials and alerts for variations or non-conformance are continuously maintained during development

3. Implement monitoring mechanisms

3.1 Implement controls to ensure mechanisms to identify software status throughout the software development life cycle are continuously maintained

3.2 Document development and maintenance of records and status reports required to show the history of baselines and their links to backups

3.3 Take action to ensure level of detail required in status reports, and identification of target audiences, meet the configuration management procedures, International Organization for Standardization (ISO), International Electrotechnical Commission (IEC) and Australian Standards (AS) and organisational requirements

3.4 Integrate configuration management into general project management processes for monitoring and control purposes and document

4. Manage release of product

4.1 Take action to ensure physical and functional completeness of items for release to all stakeholders

4.2 Identify and implement requirements for formal control of software products

4.3 Determine and document policies for retention of baseline or master copies, taking into account safety and security, legislative requirements and organisational guidelines

Evidence of the ability to:

identify and clarify configuration management requirements

identify and action control mechanisms

implement administrative and technical procedures

maintain reliable and valid technical and administrative procedures

use quality processes, audit trails and version control.

Note: Evidence must be provided for at least TWO situations or organisations.

To complete the unit requirements safely and effectively, the individual must:

compare and contrast project planning methodologies and tools

explain benchmarking methodologies when implementing monitoring mechanisms

describe how to formulate software size models and size estimates when employing control mechanisms

discuss quality assurance and quality processes when implementing monitoring mechanisms

describe software development methodologies when identifying and clarifying configuration management requirements

identify and summarise relevant organisational guidelines, legislation and codes of practice.